Virtual port based span

ABSTRACT

Methods and apparatus for performing SPAN for a virtual port are disclosed. Specifically, a frame is received from a first port. The frame or a copy thereof is transmitted to a second port, where the second port is identified in a header of the frame. At least one of the first port and the second port is a virtual port. The frame or a copy thereof is also transmitted to a third port, thereby enabling an analyzer coupled to the third port to analyze traffic received by the third port.

RELATED APPLICATIONS

This application is a divisional application of U.S. patent application Ser. No. 11/114,257, “Virtual Port Based Span,” by Sharma et al, filed on Apr. 25, 2005, which is a continuation in part of U.S. patent application Ser. No. 10/655,452, “Switch Port Analyzers,” by Kloth et al, both of which are incorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

The present invention relates to network technology. More specifically, this invention relates generally to network management and specifically relates to troubleshooting network devices that use the Fibre Channel (“FC”) protocol in a network implementing virtualization.

The Switched Port Analyzer (SPAN) feature, sometimes called port mirroring or port monitoring, selects network traffic for analysis by a network analyzer such as a SwitchProbe device or other Remote Monitoring (RMON) probe. The network analyzer is typically attached to a port that is configured to receive a copy of every frame that is sent by a particular host or hosts. This port is called a destination SPAN port. The traffic that is monitored may be ingress traffic (i.e., traffic entering the port) and/or egress traffic (i.e., traffic leaving the port). The port for which ingress and/or egress traffic is monitored is referred to as a source SPAN port. One system for performing SPAN in association with a physical source SPAN port is disclosed in patent application Ser. No. 10/655,452, entitled, “Switch Port Analyzers,” by Kloth et al, which was incorporated by reference above.

FIG. 1 is a simplified diagram illustrating an application of SPAN for use with a physical source SPAN port. In the following description, a physical source SPAN port will be referred to as a source SPAN port having a physical address. In order to initiate a SPAN session, the user configures the SPAN session 102 via a supervisor 104. Specifically, the SPAN session is configured by identifying the source SPAN port and destination SPAN port, as well as indicating whether the traffic to be monitored is ingress and/or egress traffic. The source SPAN port is typically defined by identifying both the line card and port of the line card. The destination SPAN port is also typically defined by identifying both the line card and port of the line card. For instance, a Fibre Channel port 1 of a line card 2 may be denoted as fc2/1

In this example, there are two different line cards, referred to as Intelligent Line Cards (ILCs), first line card (ILC1) 106 and second line card (ILC2) 108 having corresponding forwarding engines 110 and 112, respectively. Each network device (e.g., host or disk) is coupled to a different physical port. Specifically, with respect to the first line card 106, host 114 is associated with port fc1/1 116, the SPAN destination (SD) port 118 is associated with port fc1/5 120, and disk1 122 is associated with port fc1/7 124. With respect to the second line card 108, disk2 126 is associated with port fc2/1 128.

As one example of the application of SPAN in association with a physical source SPAN port, a user may choose to SPAN all traffic entering port fc1/1 116 and send a replica of this traffic to a SD port that is configured. In this example, the SD port 118 is configured to be port fc1/5 120. Thus, the forwarding engine 110 of the first line card (ILC1) 106 forwards frames entering port fc1/1 116 to the destination address identified in the headers of those frames, per the normal Fibre Channel forwarding protocol. In addition, the forwarding engine 110 replicates the frames so that a replica of this traffic is also forwarded to the SD port, port fc1/5 120, so that the traffic may be analyzed. Of course, the user may similarly choose to configure or select a different SD port for this particular SPAN session.

While it is helpful to perform SPAN for a physical source SPAN port, virtualization is often desirable for a variety of reasons. For instance, it may be desirable to establish virtualization of storage within a network to enable one or more physical storage locations to be logically represented by a virtual storage location. Virtualization of storage within a network such as a Storage Area Network (SAN) may be accomplished via a variety of mechanisms. One such mechanism is set forth in patent application Ser. No. 10/056,238, entitled “Methods and Apparatus for Implementing Virtualization of Storage within a Storage Area Network,” by Edsall et al, which is incorporated herein by reference for all purposes. In this manner, a physical address may be mapped to a virtual address for use in accessing a virtual storage location in a SAN.

It is also possible to configure a “virtual port.” This may be accomplished via switch-based virtualization (i.e., virtualization implemented in the switches, rather than in the hosts or storage devices). One mechanism for implementing virtual ports via a mechanism such as switch-based virtualization is further described in patent application Ser. No. 10/045,883, entitled “Methods and Apparatus for Implementing Virtualization of Storage within a Storage Area Network Through a Virtual Enclosure,” Kumar et al, which is incorporated herein by reference for all purposes. Specifically, a virtual enclosure representing one or more virtual storage units may be created, where each of the virtual storage units represents one or more physical storage locations of one or more physical storage units of a SAN. This virtual enclosure may have one or more associated virtual enclosure ports (i.e., virtual ports). Each virtual port is typically associated with a physical port of a network device within the SAN. The physical port of the network device is then instructed to handle messages addressed to the virtual port. Since each port may manage virtualization of its own traffic, virtualization capacity may scale with the number of ports on a switch.

While it is possible to configure a SPAN session for a physical source SPAN port, there is currently no mechanism to monitor traffic to or from a particular virtual port. In fact, in order to capture all the traffic related to a particular virtual interface, one would have to monitor all the physical links that carry traffic for the virtual interface. The irrelevant traffic would then need to be filtered out. This would therefore require a huge amount of fabric bandwidth and resources, even though one is only interested in traffic on a specific virtual interface. As a result, this approach is extremely inefficient.

Moreover, it is not practical to determine the physical links on which the traffic for a virtual port is flowing. Specifically, in order to identify these physical links, the routing information would need to be obtained and analyzed. However, since the routing information changes dynamically, identifying these physical links would be a difficult and computationally expensive process.

Even if it were possible to identify and monitor the physical links on which the traffic for a virtual port is flowing, a large amount of traffic for a virtual port may not travel outside the switch. As a result, such traffic would not cross a physical link. Unfortunately, the SPAN feature is not capable of capturing such internal traffic.

Moreover, a key advantage of network-based (i.e., switch-based) virtualization is that the hosts or the disks can be moved anywhere in the network, since the virtual port continues to retain the same identifier. However, according to the SPAN implementation set forth above, the SPAN configuration would need to be modified to reflect the new physical location of the hosts/disks. As a result, the SPAN configuration would need to be immediately modified for every relocation of a physical node. Otherwise there would be a window of time during which traffic would not be SPANed.

In view of the above, it would be beneficial if traffic associated with a virtual port could be effectively monitored via a SPAN feature.

SUMMARY OF THE INVENTION

Methods and apparatus for performing SPAN for virtual ports are disclosed. This is accomplished, in part, by supporting SPAN for virtual ports. In this manner, traffic associated with a virtual port may be analyzed.

In accordance with one aspect of the invention, a frame is received from a first port. The frame or a copy thereof is transmitted to a second port, where the second port is identified in a header of the frame. At least one of the first port and the second port is a virtual port. The frame or a copy thereof is also transmitted to a third port, thereby enabling an analyzer coupled to the third port to analyze traffic received by the third port. Embodiments of the invention may be implemented in a Fibre Channel network, as well as other types of networks.

In accordance with another aspect of the invention, the third port is configured as a SPAN destination port, while the first or second port is configured as a SPAN source port. The configuration information is used to determine whether frames transmitted from the first port to the second port are to be analyzed. In particular, the SPAN source port for which traffic is to be analyzed may be an ingress and/or egress port. Thus, it is possible that either the first or the second port may be configured as a SPAN source port.

In accordance with one embodiment, a virtual SPAN source port is identified by a line card, a virtualization engine on the line card, and a virtual port. For instance, the virtualization engine may include software and/or hardware such as that of a hardware ASIC of a CPU that performs virtualization operations. The virtualization engine is responsible for performing SPAN (e.g., duplicating the frame associated with the virtual SPAN source port for analysis by an analyzer coupled to the SPAN destination port). In addition, the virtualization engine is also responsible for performing virtual-physical address mapping and translation in order to route the frames to their intended destination. For instance, the virtualization engine may manage address translation to enable SCSI requests to be transmitted to the appropriate physical disks in a sequence consistent with the virtualization model that is implemented.

In accordance with yet another aspect of the invention, when a user configures a SPAN session, a first set of configuration information identifying a virtual source SPAN port for which traffic is to be analyzed is received, where the virtual port is an ingress and/or egress port. In addition, a destination SPAN port that is to receive a copy of the traffic to be analyzed is identified. For instance, the destination SPAN port may be selected by the user or may be pre-configured. Thus, the first set of configuration information may identify the virtual source SPAN port, the destination SPAN port, and indicate whether the virtual source SPAN port is an ingress and/or egress port for purposes of traffic forwarding and analysis. A second set of configuration information associated with the first set of configuration information is then transmitted to a line card associated with the virtual source SPAN port, thereby enabling the line card to transmit a copy of frames for which traffic is to be analyzed for the virtual source SPAN port to the destination SPAN port. The second set of information should also identify the virtual source SPAN port, the destination SPAN port, and indicate whether the virtual source SPAN port is an ingress and/or egress port for purposes of traffic forwarding and analysis.

In accordance with one embodiment, the line card and virtualization engine are identified by the user in the first set of configuration information. As one example, a virtual source SPAN port may be identified by an interface name, which identifies the line card, the virtualization engine, and the port.

In accordance with another embodiment, the second set of configuration information is transmitted to the virtualization engine of the line card. Since the line card is responsible for performing SPAN, performing virtual-physical address mapping, and frame forwarding, the virtualization engine needs to be able to identify the virtual source SPAN port. For instance, in order to route frames in a Fibre Channel network, a Fibre Channel Address, referred to as an FCID, is used. In addition, when implemented in a network implementing virtualization, such as a VSAN, the correct VSAN should be identified. Thus, in a Fibre Channel network, the second set of configuration information may identify the virtual source SPAN port via both the FCID and the VSAN that together uniquely identify the virtual source SPAN port, rather than the interface name used to configure the SPAN session.

In accordance with another embodiment, a supervisor is responsible for ensuring that a line card is configured for a particular SPAN session. Specifically, the supervisor receives the first set of configuration information and transmits the appropriate second set of configuration information to the line card. In addition, the supervisor is also responsible for removing a SPAN session configuration from a particular line card, as appropriate. This may be desirable, for example, if a virtual port has been deleted or a SPAN session has been discontinued.

These and other features and advantages of the present invention will be presented in more detail in the following specification of the invention and the accompanying figures, which illustrate by way of example the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified diagram illustrating an application of SPAN for use with a physical source SPAN port.

FIG. 2 is a simplified block diagram illustrating a system configured for implementing SPAN for a virtual source SPAN port in accordance with one embodiment of the invention.

FIG. 3 is an exemplary representation of a SPAN session that may be configured.

FIG. 4 is a general block diagram illustrating a system in which the present invention may be implemented in accordance with one embodiment of the invention.

FIG. 5 is a transaction flow diagram illustrating a method of creating a virtual port and configuring SPAN information associated with the virtual port.

FIG. 6 is a transaction flow diagram illustrating a method of updating the SPAN information associated with a virtual port when the virtual port is deleted or a SPAN session is discontinued.

FIG. 7 is a diagrammatic representation of a router in which embodiments of the present invention may be implemented.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

Reference will now be made in detail to a specific embodiment of the invention. An example of this embodiment is illustrated in the accompanying drawings. While the invention will be described in conjunction with this specific embodiment, it will be understood that it is not intended to limit the invention to one embodiment. On the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. The present invention may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail in order not to unnecessarily obscure the present invention. Embodiments of the invention support SPAN in a network such as a Fibre Channel network to enable traffic associated with a virtual source SPAN port to be analyzed. In the following description, the embodiments will be described with reference to a Fibre Channel network. However, the disclosed embodiments may also be applied in other types of networks that support virtualization and in which traffic is to be analyzed, such as Ethernet, TCP/IP, ISCSI, FCIP.

There are numerous advantages to performing SPAN for a virtual port. For instance, some frames may not traverse a physical interface. This may occur, for example, if a frame is consumed entirely within the line card. As another example, a frame may be generated entirely within the line card. Since these frames may not traverse a physical interface, the frames cannot be analyzed by performing SPAN for a physical interface. For these reasons, it may be desirable to perform SPAN for a virtual source SPAN port rather than a physical source SPAN port.

In accordance with various embodiments, a virtual port may be a Fibre Channel Node port (N-port) of a virtual enclosure representing one or more virtual storage units, where each of the virtual storage units represents one or more physical storage locations of one or more physical storage units of a SAN. Thus, each virtual port is associated with a physical port of a network device within the SAN. The physical port of the network device is instructed to handle messages addressed to the virtual port. Of course, there are instances where traffic for a virtual port may not exist on a physical port, such as where traffic is generated and processed internally.

The virtual N-port (NV port) may connect to a virtual Fabric port (FV port). In addition, traffic for a NV port can flow through one or more physical ports, since there could be frames from or to different physical ports for that particular virtual port. Conversely, a physical port may carry traffic corresponding to many NV ports.

FIG. 2 is a simplified block diagram illustrating a system configured for implementing SPAN for a virtual source SPAN port in accordance with one embodiment of the invention. In order to configure a SPAN session, a user may submit configuration information at 202. A supervisor 204 obtains the configuration information from the user. For instance, the configuration information may identify the virtual source SPAN port, as well as indicate whether the source SPAN port is an ingress and/or egress port. The configuration information may also identify the SD port, where the SD port is configured by the user rather than pre-configured. The supervisor 204 may then store the configuration information for subsequent SPAN sessions. In addition, the supervisor 204 transmits the configuration information to the appropriate line card(s) so that the line card(s) may be programmed.

In this example, there are two line cards, referred to as Intelligent Line Cards (ILCs), first line card (ILC1) 206 and second line card (ILC2) 208, having corresponding forwarding engines 210 and 212, respectively, which may be capable of forwarding traffic associated with a physical port, as well as performing SPAN associated with a physical port.

In addition, in order to support SPAN in a system supporting virtualization, virtual-physical address mapping functionality is provided to support mapping from virtual to physical addresses, and vice versa. In accordance with one embodiment, this mapping functionality is implemented in a virtualization engine. Thus, each line card has at least one virtualization engine associated therewith. In this example, the line cards 206, 208 each include at least one virtualization engine 214, 216, respectively. In particular, a virtualization engine is capable of handling a maximum number of ports. As a result, each line card may include a plurality of virtualization engines to maximize the traffic throughput for that line card.

In accordance with one embodiment, since virtual-physical address mapping is performed by the virtualization engine(s) 214, 216 for a virtual source SPAN port, the virtualization engine(s) 214, 216 are also responsible for performing forwarding and SPAN associated with the virtual source SPAN port. In other words, the appropriate one of the virtualization engine(s) 214, 216 replicates frames associated with the virtual source SPAN port and forwards them to the appropriate SD port after the appropriate address mapping is performed, in addition to forwarding the original frames to their intended destination. Each virtualization engine may be implemented in hardware, software, or a combination thereof.

The first line card ILC1 206 has a set of interfaces 218, 220, 222 and the second line card ILC2 208 has a set of interfaces 224, 226, 228. Each of the interfaces may be coupled to a network device such as a host or memory (e.g., disk). In addition, any of the interfaces may be configured as the SPAN destination (SD) port. In this example, a host 230 is coupled to the interface 218, the interface 220 is configured as the SD port 232, and disks Disk1 234 and Disk2 236 are coupled to the interfaces 222 and 228, respectively. An analyzer may be coupled to the SD port at 232, as shown, for analyzing frames received by the SD port.

In accordance with one embodiment, each virtual interface has an associated interface name, while each physical interface has an associated FCID. In particular, a physical interface has an interface name that identifies both the line card and the port. For instance, the interface name for a physical port may be represented by “line card/port.” For instance, as shown in FIG. 2, interface 220 has an interface name “fc1/9,” which denotes port 9 of line card 1.

A virtual port may similarly be identified by the line card and port. In accordance with one embodiment, a virtual port is further identified by a virtualization engine of the line card that is to process traffic associated with the virtual port. Since the traffic for virtual ports is divided among a plurality of virtualization engines, the traffic for virtual ports may be more efficiently processed. Thus, in order to identify a virtual port, the virtual port may have an interface name which may be represented by “line card/virtualization engine/port.” For instance, as shown in FIG. 2, the interface 218 has associated interface name “fv1/1/1,” which denotes port 1 of the first virtualization engine of line card 1. As another example, the interface 222 has associated interface name “fv1/2/1,” which denotes port 1 of the second virtualization engine of line card 1. Similarly, the interface 228 has associated interface name “fv2/1/1,” which denotes port 1 of the first virtualization engine 1 of line card 2.

As set forth above, in order to initiate a SPAN session, a user may configure the SPAN session by submitting a set of configuration information. Specifically, a user may configure a SPAN session via a graphical user interface such as that illustrated in FIG. 3. In this example, the user configures a SPAN session by entering or otherwise selecting a set of configuration information, which indicates the virtual source SPAN port, destination SPAN port, and direction of traffic to be SPANed (e.g., IN/OUT/BOTH). Thus, the user configures a source SPAN port for which traffic is to be duplicated and transmitted to a SD port for analysis. In this example, the source SPAN port is a virtual port that is identified by interface name “fv2/1/1,” shown as interface 228 in FIG. 2. Thus, traffic for port 1 of the first virtualization engine of line card 2 is to be analyzed. In addition, the user configures a destination SPAN port to receive a copy of the traffic to be analyzed. In this example, the SD port is configured to be “fc1/9,” representing physical port 9 of line card 1, shown as interface 220 in FIG. 2. The user may then indicate whether the virtual port identified as the source SPAN port is an ingress and/or egress port. In other words, the user may indicate whether the traffic flowing through the virtual source SPAN port and therefore the traffic to be analyzed is flowing into the virtual port and/or out of the virtual port. In this example, the user indicates that the port is the SPAN source in both the ingress and egress direction for purposes of traffic analysis. In accordance with one embodiment, the SPAN session configuration is stored in persistent memory. In other words, when a SPAN session is configured, it will be retained across reboots.

Once the SPAN session is configured, the appropriate information is transmitted to the first line card, enabling the line card to transmit a copy of frames for which traffic is to be analyzed for the virtual source SPAN port to the destination SPAN port. Specifically, a set of configuration information identifying the virtual source SPAN port, the SD port, and indicating whether the virtual source SPAN port is an ingress and/or egress port is provided to the first line card. The line card then ensures that copies of the frames flowing through the virtual source SPAN port are transmitted to the SD port, as configured for that particular SPAN session. In accordance with one embodiment, the SD port is configured to disregard the buffer-to-buffer credit flow control mechanism of the Fibre Channel protocol.

In this example, when a frame flows into or out of the virtual source SPAN port at interface 228 of FIG. 2, virtual-physical address mapping is performed. The frame is transmitted to its intended destination, while a copy of the frame is forwarded to the SD port at interface 220. An analyzer coupled to the SD port at 232 may then analyze the traffic received by it.

SPAN may be implemented for a virtual port through a variety of system configurations. FIG. 4 is a general block diagram illustrating a system in which the present invention may be implemented in accordance with one embodiment of the invention. As shown in FIG. 4, supervisory functions performed outside the line card are represented by boxes above dotted line 400, while functions performed inside the line card are represented by boxes below the dotted line 400. In accordance with one embodiment, supervisory functions are performed by a supervisor, which may be implemented in hardware and/or software.

In accordance with one embodiment, virtual ports are created at the line card. In this example, a Node port (Nport) Creator 402 is responsible for creating virtual ports (e.g., N-ports). More particularly, the Nport Creator 402 obtains configuration information associated with one or more Virtual Storage Area Networks (VSANs). For instance, the VSAN configuration information may indicate that a particular VSAN requires a particular number of virtual interfaces. For each interface that is “requested,” the Nport Creator may create a virtual port that is associated with that VSAN. Specifically, each virtual port is assigned a port Worldwide Name (WWN). In addition, in accordance with one embodiment, each virtual port is associated with a virtualization engine of the line card.

Once a virtualization engine has been associated with the virtual port, an interface name, which may be represented by “line card/virtualization engine/port,” may also be associated with the virtual port. In accordance with one embodiment, the FV port daemon 404 is responsible for creating this interface name. When the interface name is provided to the Nport Creator 402, the Nport Creator 402 links the interface name to the WWN assigned by the Nport Creator to the virtual port. Each time the line card is rebooted, a new FCID is allocated to the virtual port by Fport server 407. The FCID allocated by the Fport server 407 is then associated with the VSAN identifier and interface name of the virtual port.

It is important to note that the FCID associated with a virtual port does not remain constant. Therefore, in order to route a particular frame in association with a virtual source

SPAN port and perform SPAN for that frame, the FCID associated with the virtual source SPAN port must be obtained. In accordance with one embodiment, when a user configures a SPAN session for a virtual source SPAN port via a graphical user interface at 406, this configuration information is provided to a SPAN Manager 408, which then forwards the appropriate configuration information to LC SPAN manager 412 of the line card. For instance, the interface name may be provided to the LC SPAN manager 412 so that the corresponding FCID may be obtained. The LC SPAN Manager 412 then obtains the FCID and VSAN identifier for the virtual source SPAN port so that the corresponding frame can be processed. This may be accomplished by identifying the VSAN and FCID associated with the interface name of the virtual source SPAN port. In accordance with one embodiment, the LC SPAN Manager 412 sends the interface name corresponding to the virtual source SPAN port to Fport server 407. The Fport server 407 then looks up the interface name to identify the corresponding VSAN and FCID that together uniquely identify the virtual port, which it then provides to the LC SPAN Manager 412. The LC SPAN manager 412 then provides the VSAN identifier and FCID, along with other pertinent SPAN configuration information, such as SD port and an indicator as to whether the source SPAN port is an ingress and/or egress port, to the Virtualization Engine 414 of the line card. The Virtualization Engine 414 may then store the information for the SPAN session to enable traffic to be processed accordingly.

Once the Virtualization Engine 414 has received the VSAN identifier and FCID that uniquely identifies the virtual source SPAN port, it can process traffic for the virtual port. More particularly, the Virtualization Engine 414 duplicates frames associated with the virtual source SPAN port and transmits those frames to the SD port. For instance, the Virtualization Engine 414 may obtain the FCID and VSAN identifier from the header of the frame to look up the FCID and VSAN in the SPAN session information such that the SD port and other information for the SPAN session can be determined. In addition, the Virtualization Engine 414 also performs the appropriate virtual-physical address mapping in order to forward frames to the intended destination. For instance, the virtualization engine may manage address translation to enable SCSI requests to be transmitted to the appropriate physical disks in a sequence consistent with the virtualization model that is implemented.

FIG. 5 is a transaction flow diagram illustrating a method of creating a virtual port (e.g., to enable a SPAN session associated with the virtual port to be configured or to activate an existing SPAN session that involves a virtual port) and configuring a SPAN session associated with the virtual port in a system such as that described above with reference to FIG. 4. As shown, interactions between Nport Creator 502, Port Daemon (PD) 504, Fport Server 506, SPAN manager 508, LC SPAN manager 510, and virtualization engine 512 are represented by corresponding labeled vertical lines.

Two different scenarios are illustrated in FIG. 5. First, the steps performed to create a virtual port (e.g., to enable a SPAN session associated with the virtual port to be created or to activate an existing SPAN session that involves a virtual port) are illustrated in steps 514 through 530. Second, the steps performed to create a SPAN session for an existing virtual port are illustrated in steps 532 through 546.

In order to initially create a SPAN session for a virtual port or activate an existing SPAN session for a virtual port, the virtual port must be created. As described above, in accordance with one embodiment, the Nport Creator 502 of the line card creates one or more virtual ports as needed for each existing SPAN session. Each virtual port has an associated WWN.

When the line card is rebooted or when it first comes up, the Nport Creator identifies which VSANs need virtual interfaces. For instance, the Nport Creator may obtain VSAN configuration information to identify the number of virtual interfaces associated with each VSAN. The Nport Creator may then create one or more virtual ports, as necessary. For each virtual port that is created, the virtual port is assigned a WWN by the Nport Creator and associated with a particular VSAN at 513.

Once the Nport Creator creates a virtual port, the Nport Creator may log in the virtual port. Specifically, the Nport Creator performs a fabric login (FLOGI) for the virtual port (e.g., by specifying the WWN for the virtual port) at 514. In accordance with one embodiment, the FVPD creates an interface name and provides the interface name for the WWN to the Nport Creator at 516. The Nport Creator then associates the interface name with the virtual port, and therefore with the WWN and VSAN. The FVPD may then notify the SPAN manager that the interface name has been created at 518. For instance, the processing performed by various system components may be initiated upon notification that the interface name has been created.

In order for a Fibre Channel node to establish a logical connection to a fabric switch, it performs a fabric login (FLOGI). Unlike many LAN technologies that use a fixed Media Access Control (MAC) address, Fibre Channel uses an address identifier, referred to as an FCID, which is dynamically assigned during login. Thus, in accordance with one embodiment, the Nport Creator 502 requests an FCID for a virtual port on a particular VSAN. Specifically, the Nport Creator 502 provides the VSAN identifier at 520 to the Fport Server by performing an FLOGI (e.g., by specifying the port WWN). The Fport Server then assigns an FCID to the virtual port and provides the FCID and VSAN identifier to the Nport Creator at 522. Through the use of both the FCID and VSAN, the virtual port may be identified.

In addition, the Fport Server may notify the Nport Creator that the virtualization engine needs to be programmed. Thus, in accordance with one embodiment, the Nport Creator then sends a PRE_INIT message at 524 to the SPAN manager indicating that the virtual port has logged in and that the virtualization engine now needs to be programmed. The PRE_INIT message may include the interface name, FCID and the VSAN identifier that is associated with that virtual port. The SPAN manager may then store the VSAN identifier and interface name in a table or other suitable data structure for tracking virtual ports. The SPAN manager may then sends a PRE_INIT response message at 526 to the Nport Creator acknowledging that it should now program the corresponding virtualization engine. The Nport Creator programs the appropriate virtualization engine at 527. In particular, the virtualization engine is programmed to enable traffic for a virtual port to be processed by the virtualization engine. For instance, the interface name may be associated with the VSAN identifier and FCID. The Nport Creator then notifies the Fport Server that the appropriate virtualization engine has been programmed for the virtual port at 528. The Fport Server then sends a response to the Nport Creator at 530 acknowledging that the virtualization engine has been programmed for the virtual port. The Fport Server may now notify the SPAN manager that frames for the virtual port may now be processed.

In accordance with one embodiment, the Fport Server is responsible for notifying the SPAN manager that the virtual port has logged in and that the virtualization engine has been programmed for the virtual port. This may be desirable, since the SPAN manager may now enable a user to select this particular virtual port during the configuration of a SPAN session. As shown at 532, the Fport Server sends a message to the SPAN manager that indicates that frames associated with the virtual port, identified by the corresponding port WWN or interface name, can now be processed by the corresponding virtualization engine.

When a user configures a SPAN session at 534, the user enters or otherwise selects configuration information for the SPAN session. Specifically, the configuration information indicates a SPAN source port (e.g., interface name), a SPAN destination port, and an indication of whether the traffic being spanned is ingress and/or egress traffic. For instance, the user may indicate whether the traffic to be analyzed is IN and/or OUT.

Once the user has configured the SPAN session, the SPAN manager may look up the VSAN identifier for the interface name that has been configured. The SPAN manager may then send the interface name and optionally the VSAN identifier to the LC SPAN manager at 536. The LC SPAN manager queries the Fport server for the FCID (and the VSAN identifier if not previously provided to it by the SPAN manager) corresponding to the interface name at 538. The Fport server then provides the FCID and VSAN to the LC SPAN manager at 540. The FCID, VSAN, and associated configuration information (e.g., Destination SPAN port and whether traffic to be monitored is ingress and/or egress) are then provided to the virtualization engine at 542.

The virtualization engine 512 may then send a response indicating success or failure of the SPAN session configuration at 544. This response may then be forwarded to the SPAN manager at 546. If the configuration of the virtualization engine has been successful, the virtualization engine proceeds to process traffic for the configured SPAN session. Specifically, the virtualization engine proceeds to perform virtual-physical address mapping for traffic associated with the source SPAN port and forward traffic accordingly, as well as perform SPAN for the configured SPAN session. Frames that are forwarded may be transmitted via hardware, or may be sent directly to their intended destination by passing the hardware.

In accordance with one embodiment, when a frame is received (e.g., by the virtualization engine), it is determined whether SPAN needs to be performed for that frame. In other words, the line card determines whether a corresponding SPAN session has been configured. For instance, the virtualization engine may search for a SPAN entry identifying a source SPAN port from which a frame was received (e.g., for ingress traffic) or to which the frame is to be transmitted (e.g., for egress traffic). For each frame having a corresponding SPAN entry, SPAN is performed.

SPAN is performed continuously as configured until SPAN configuration information is changed in one of two ways. First, it may be desirable to delete a virtual port. For instance, a user may wish to delete or re-configure a virtual port, such as when the functionality or service provided by the virtual port is no longer needed. Second, a user may choose to discontinue a particular SPAN session. In either instance, the SPAN session is deleted.

FIG. 6 is a transaction flow diagram illustrating a method of updating the SPAN information associated with a virtual port when the virtual port is deleted or a SPAN session is discontinued. When a virtual port has been deleted, the line card logs out the virtual port. In accordance with one embodiment, the Nport creator sends a fabric logout (FLOGO) identifying the WWN of the virtual port at 602 to the Fport Server. The Fport Server sends a response confirming the fabric logout of the virtual port at 604 to the Nport Creator.

In accordance with one embodiment, the Fport Server is responsible for notifying the SPAN manager that the virtual port is no longer logged in. This may be desirable, since the SPAN manager may now prevent a user from selecting or entering this particular virtual port during the configuration of a SPAN session. As shown at 606, the Fport Server sends a message to the SPAN manager that indicates that frames associated with the virtual port, identified by the corresponding port WWN or interface name, can no longer be processed by the corresponding virtualization engine.

The Nport Creator also notifies the Port Daemon that the virtual port has been logged out at 608. The Port Daemon acknowledges that the virtual port is no longer logged in at 610. The Port Daemon may then notify the SPAN manager that the virtual port has been removed (or logged out) at 612. In order to remove the virtual port, the virtualization engine is programmed at 614. For instance, the interface name may no longer be recognized as a virtual port in association with the VSAN and FCID.

As set forth above, when a virtual port is removed, it is no longer functional as a SPAN port. Thus, in addition to removing the virtual port, if that virtual port has previously been configured as a source SPAN port, that configuration information needs to be updated. Of course, even if the virtual port has not been removed, a user may choose to discontinue a particular SPAN session. Thus, the configuration of a virtual port as a source SPAN port may be deleted by a user as shown at 615. In either case, the configuration information associated with the virtual port is removed from the appropriate entities.

In order to remove the configuration information associated with a source SPAN port, the SPAN manager identifies the virtual port (e.g., via interface name) from the message received from the Port Daemon at 612 or 615. Upon receiving the interface name, the SPAN manager may look up the corresponding VSAN for the virtual port. The SPAN manager may then send a message to the LC SPAN manager to request that the LC SPAN manager remove the configuration information for the virtual port from the line card at 616 (e.g., by specifying the interface name and optionally the VSAN of the virtual port). The LC SPAN manager may then request the FCID (and VSAN, as appropriate) associated with the virtual port from the Fport Server at 618 (e.g., by specifying the interface name). The Fport Server looks up the interface name to identify the corresponding FCID and VSAN at 620 and provides the FCID and VSAN that together uniquely identify the virtual port to the LC SPAN manager at 620. The LC SPAN manager then instructs the appropriate virtualization engine to remove the SPAN entry corresponding to the FCID and VSAN at 622. In this manner, a SPAN entry identifying the SD SPAN port and indicating whether ingress and/or egress frames associated with the virtual port are to be SPANed is removed. The virtualization engine may then indicate to the LC SPAN manager whether the re-configuration was successful by sending a response to the LC SPAN manager at 624. The LC SPAN manager may then forward this response to the SPAN manager at 626.

The apparatus (e.g. switch or router) of this invention may be specially constructed for the required purposes, or may be a general purpose programmable machine selectively activated or reconfigured by a computer program stored in memory. The processes presented herein are not inherently related to any particular switch or other apparatus.

Generally, the techniques of the present invention may be implemented on software and/or hardware. For example, it can be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, or on a network interface card.

A software or software/hardware hybrid route optimization system of this invention is preferably implemented on a general-purpose programmable machine selectively activated or reconfigured by a computer program stored in memory. Such programmable machine may be a network device designed to handle network traffic. Such network devices typically have multiple network interfaces including frame relay, ISDN, and wireless interfaces, for example. Specific examples of such network devices include routers and switches. For example, the systems of this invention may be specially configured switches such as the MDS series of Fibre Channel switches, including Cisco MDS series 9200 and 9500 available from Cisco Systems, Inc. of San Jose, Calif. A general architecture for some of these machines will appear from the description given below. In an alternative embodiment, the SPAN methods and system may be implemented on a general-purpose network host machine such as a personal computer or workstation, appliance, or storage device. Further, the invention may be at least partially implemented on a card (e.g., an interface card) for a network device or a general-purpose computing device.

Referring now to FIG. 7, a network device 1060 suitable for implementing the techniques of the present invention includes a master central processing unit (CPU) 1062, interfaces 1068, and a bus 1067 (e.g., a PCI bus). When acting under the control of appropriate software or firmware, the CPU 1062 may be responsible for implementing specific functions associated with the functions of a desired network device. For example, when configured as an intermediate router, the CPU 1062 may be responsible for analyzing frames, encapsulating frames (or packets), and forwarding frames for transmission to a set-top box. The CPU 1062 preferably accomplishes all these functions under the control of software including an operating system (e.g. Windows NT), and any appropriate applications software.

CPU 1062 may include one or more processors 1063 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 1063 is specially designed hardware for controlling the operations of network device 1060. In a specific embodiment, a memory 1061 (such as non-volatile RAM and/or ROM) also forms part of CPU 1062. However, there are many different ways in which memory could be coupled to the system. Memory block 1061 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, etc.

The interfaces 1068 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data frames over the network and sometimes support other peripherals used with the network device 1060. Among the interfaces that may be provided are Fibre Channel ports, Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided, such as fast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces, ASI interfaces, DHEI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as frame switching, media control and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 1062 to efficiently perform routing computations, network diagnostics, security functions, etc.

Although the system shown in FIG. 7 illustrates one specific network device of the present invention, it is by no means the only network device architecture on which the present invention can be implemented. For example, an architecture having a single processor that handles communications as well as routing computations, etc. is often used. Further, other types of interfaces and media could also be used with the network device.

Regardless of the network device's configuration, it may employ one or more memories or memory modules (such as, for example, memory block 1065) configured to store data, program instructions for the general-purpose network operations and/or other information relating to the functionality of the techniques described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example.

Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine-readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). The invention may also be embodied in a carrier wave traveling over an appropriate medium such as airwaves, optical lines, electric lines, etc. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.

In accordance with various embodiments of the invention, it is possible to monitor (and analyze) traffic associated with a virtual port independent of the location of any associated hosts or disks. Of course, traffic monitoring and analysis may be implemented using a variety of processes or applications. For instance, such applications may obtain information from the frames such as a Logical Unit (LUN), Logical Block Address (LBA) range, data patterns, type of I/O, etc. For instance, the type of I/O may include such as read or write, as well as control commands. In addition, traffic monitoring and analysis may be performed with frames sent in accordance with a variety of protocols, such as Ethernet, iSCSI, FCIP, iFCP, and IPFC. This may desirable, for instance, in order to debug a particular protocol such as an in-house protocol (e.g., interlocking) For instance, a virtual port for IPFC termination may be identified in a SPAN session to debug the IPFC protocol. In this manner, traffic on a particular link specific to an in-house protocol may be captured and analyzed.

In the above description, the term “frame” is used throughout. However, the term “frame” is intended to be used interchangeably with the term “packet.” Accordingly, the term “frame” is intended to be interpreted broadly rather than narrowly.

While the invention has been particularly shown and described with reference to specific embodiments thereof, it will be understood by those skilled in the art that changes in the form and details of the disclosed embodiments may be made without departing from the spirit or scope of the invention. For instance, it will be appreciated that at least a portion of the functions described herein could be performed by one or more devices, e.g., by a microprocessor, by a cluster of microprocessors, etc. Considering these and other variations, the scope of the invention should be determined with reference to the appended claims. 

1. In a network device, a method of performing configuration to analyze traffic in a virtual storage area network, comprising: receiving a first set of configuration information identifying a virtual port for which traffic is to be analyzed, the virtual port being at least one of an ingress port and an egress port; and identifying a destination port to receive a copy of the traffic to be analyzed.
 2. The method as recited in claim 1, further comprising: transmitting a second set of configuration information associated with the first set of configuration information to a line card associated with the virtual port, thereby enabling the line card to transmit a copy of frames for which the traffic is to be analyzed for the virtual port to the destination port.
 3. The method as recited in claim 1, wherein the virtual port is associated with a virtualization engine of the line card, wherein transmitting the second set of configuration information to the line card comprises: transmitting the second set of configuration information to the virtualization engine of the line card, thereby enabling the virtualization engine to transmit a copy of frames for which the traffic is to be analyzed for the virtual port to the destination port.
 4. The method as recited in claim 1, wherein the first set of configuration information further identifies the line card.
 5. The method as recited in claim 4, wherein the first set of configuration information further identifies a virtualization engine of the line card, wherein transmitting the second set of configuration information to the line card comprises: transmitting the second set of configuration information to the virtualization engine of the line card, thereby enabling the virtualization engine to transmit a copy of frames for which the traffic is to be analyzed for the virtual port to the destination port.
 6. The method as recited in claim 5, wherein the virtualization engine is responsible for mapping a virtual address associated with the virtual port to a physical address.
 7. The method as recited in claim 1, further comprising: obtaining the second set of configuration information associated with the first set of configuration information.
 8. The method as recited in claim 7, wherein obtaining the second set of configuration information comprises: obtaining a FCID associated with the virtual port.
 9. The method as recited in claim 1, wherein the second set of configuration information identifies the destination port, a virtual storage area network identifier and a FCID associated with the virtual port, and indicates that the virtual port is at least one of an ingress and an egress port.
 10. The method as recited in claim 1, wherein the second set of configuration information identifies the destination port, the virtual port, and indicates that the virtual port is at least one of an ingress and an egress port.
 11. The method as recited in claim 1, wherein the first set of configuration information and the second set of configuration information are different.
 12. A non-transitory computer-readable storage medium storing thereon computer-readable instructions, comprising: instructions for obtaining a first set of configuration information identifying a virtual port for which traffic is to be analyzed, the virtual port being at least one of an ingress port and an egress port; and instructions for identifying a destination port to receive a copy of the traffic to be analyzed.
 13. The non-transitory computer-readable medium as recited in claim 12, further comprising: instructions for transmitting a second set of configuration information associated with the first set of configuration information to a line card associated with the virtual port, thereby enabling the line card to transmit a copy of frames for which the traffic is to be analyzed for the virtual port to the destination port.
 14. The non-transitory computer-readable medium as recited in claim 12, wherein the virtual port is associated with a virtualization engine of the line card, wherein transmitting the second set of configuration information to the line card comprises: transmitting the second set of configuration information to the virtualization engine of the line card, thereby enabling the virtualization engine to transmit a copy of frames for which the traffic is to be analyzed for the virtual port to the destination port.
 15. The non-transitory computer-readable medium as recited in claim 1, wherein the first set of configuration information further identifies the line card.
 16. The non-transitory computer-readable medium as recited in claim 15, wherein the first set of configuration information further identifies a virtualization engine of the line card, wherein transmitting the second set of configuration information to the line card comprises: transmitting the second set of configuration information to the virtualization engine of the line card, thereby enabling the virtualization engine to transmit a copy of frames for which the traffic is to be analyzed for the virtual port to the destination port.
 17. The non-transitory computer-readable medium as recited in claim 16, wherein the virtualization engine is responsible for mapping a virtual address associated with the virtual port to a physical address.
 18. An apparatus, comprising: a processor; and a memory, at least one of the processor or the memory being configured for: obtaining a first set of configuration information identifying a virtual port for which traffic is to be analyzed, the virtual port being at least one of an ingress port and an egress port; and identifying a destination port to receive a copy of the traffic to be analyzed.
 19. The apparatus as recited in claim 18, at least one of the processor or the memory being configured for performing steps, further comprising: obtaining the second set of configuration information associated with the first set of configuration information.
 20. The apparatus as recited in claim 19, wherein obtaining the second set of configuration information comprises: obtaining a FCID associated with the virtual port.
 21. The apparatus as recited in claim 18, wherein the second set of configuration information identifies the destination port, a virtual storage area network identifier and a FCID associated with the virtual port, and indicates that the virtual port is at least one of an ingress and an egress port.
 22. The apparatus as recited in claim 18, wherein the second set of configuration information identifies the destination port, the virtual port, and indicates that the virtual port is at least one of an ingress and an egress port.
 23. The apparatus as recited in claim 18, wherein the first set of configuration information and the second set of configuration information are different. 